IBP Signal Issue #16 merger integration and decision continuity hero image
FULL PUBLIC ISSUE

On September 17, 2026, 4flow and Kinaxis hosted a webinar with Evermark titled "From rapid mobilization to measurable value: Evermark's Kinaxis transformation journey with 4flow." The webinar description positioned Evermark's experience as a transformation journey during major business change: the kind of structural transition that separates companies that maintain decision continuity from those that fragment.

Evermark merger completed January 20, 2026. The company has approximately $1.9B annual retail sales. Webinar speakers include Evermark Head of IT Andrew Scozzafava and 4flow VP Consulting Akhilesh Mohan.

What happens after the merger closes but before the planning model integrates? Between Day 1 and Day 90, two legacy planning teams operate on disconnected baselines. Demand assumptions diverge. Inventory policies conflict. Capacity allocation optimizes for legacy organizations, not the combined entity. The integration team focuses on ERP harmonization, master data alignment, and system migration. Meanwhile, decisions that require cross-functional trade-offs fragment across functional silos.

This is the decision continuity gap. It is not a technology problem. It is not a process maturity problem. It is a decision architecture problem.

Note on Day 1/30/90 framing: The Day 1/30/90 timeline used throughout this article is a heuristic for sequencing, not a universal prescription or industry-standard milestone. Actual timing should be adapted to your M&A/structural change context, regulatory requirements, and organizational readiness. The framework proposes relative sequencing (immediate → near-term → medium-term), not fixed deadlines.

Pattern Detected: The decision continuity gap

Most M&A integration playbooks treat planning integration as a technology and process challenge:

These are necessary investments. They are also slow. ERP harmonization takes months. Master data alignment takes quarters. IBP process integration takes years. Meanwhile, the combined entity must make decisions now: about inventory positioning, customer commitments, capacity allocation, and cash deployment.

The structural failure occurs at the decision layer, not the system layer. Day 1 after close: two planning teams, two demand baselines, two inventory policies, two cost structures. Each legacy team optimizes for its historical organization. Cross-functional trade-offs: the decisions that determine whether the merger creates value: remain unresolved because no one owns the combined decision.

By Day 30, functional handoffs have optimized local metrics while systemic trade-offs languish. Demand optimizes for service. Supply optimizes for cost. Finance optimizes for cash. Product optimizes for roadmap. The combined entity operates on disconnected decision baselines while integration teams celebrate system migration milestones.

By Day 90, the organization has institutionalized parallel planning processes that cannot govern interdependent decisions. The merger is legally complete. The planning model remains fragmented.

IBP implication: A Minimum Viable Decision System

The appropriate response is not a full IBP redesign during structural change. It is a Minimum Viable Decision System (MVDS): a temporary decision architecture that ensures continuity while permanent structures are built. MVDS is technology-neutral: it can be implemented with any planning technology, manually, or through informal processes. MVDS is not a vendor solution, software platform, or permanent operating model.

MVDS is not a permanent IBP operating model. It is a bridge: a scaffold that prevents decision fragmentation while the permanent structure is designed and implemented. The framework proposes three phasing anchors:

Day 1: Decision continuity

At close (or immediately after), identify three to five cross-functional decision baselines that cannot be optimized independently. Examples:

For each baseline, document:

  1. Decision owner: who can accept the consequence
  2. Decision trigger: what condition requires escalation
  3. Decision alternatives: what options are on the table
  4. Trade-off metric: what is being optimized (margin, service, cash, risk)
  5. Decision timestamp: when the decision was made and when it expires

This is not a full IBP process. It is a decision continuity mechanism: a temporary scaffold that prevents fragmentation.

Day 30: Common planning language

Within 30 days, enable cross-functional trade-off discussions without requiring full process integration. The requirement is not a common planning system or unified data model. It is a language for having cross-functional conversations.

The five decision elements enable trade-off conversations:

Each element is a conversation starter, not a process artifact. The goal is not documentation. It is decision velocity.

Day 90: Connected cross-functional decisions

Enable interdependent decisions to be made together rather than sequenced through functional handoffs. Decision records capture interdependencies explicitly:

This is not a permanent IBP operating model. It is a bridge that enables connected decisions while the permanent model is being designed and implemented.

Beyond Day 90: Optimization

Once decision continuity is established, common language is operational, and cross-functional decisions are connected, the organization can optimize for IBP maturity, technology capability, and process excellence. MVDS is not the destination. It is the bridge.

Your Cycle This Week

This week, identify one cross-functional decision that is currently optimized within a single function.

Examples:

Document the decision using the five MVDS elements:

  1. Who owns the consequence?
  2. What trigger would require escalation?
  3. What alternatives are on the table?
  4. What metric is being optimized?
  5. When was the decision made, and when does it expire?

Bring this to your next Reconciliation or S&OP pre-meeting. The goal is not to solve it immediately. The goal is to make the trade-off visible.

Question Worth Asking

"For your next M&A, divestiture, or structural change: What three decisions would fragment if you did not define them before Day 1?"

Write them down. Assign owners. Schedule the conversation.

Sources

This article is for informational purposes only and does not constitute consulting advice. The MVDS framework is presented as a heuristic, not a vendor-prescribed solution. No quantified Evermark outcomes, ROI, or KPIs are claimed. EY sources provide conceptual support for decision orchestration; they do not constitute customer evidence or endorsement.